Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0923

reference: 368-tree-1
name: 0923
tree-preservation-order: undefined
368-tpo-1
uprn
address-text
point: POINT (-1.015986 50.894769)
geometry: MULTIPOLYGON (((-1.015887 50.894759,-1.015891 50.894778,-1.015905 50.894796,-1.015927 50.894810,-1.015954 50.894819,-1.015985 50.894823,-1.016016 50.894820,-1.016044 50.894811,-1.016066 50.894797,-1.016080 50.894780,-1.016086 50.894761,-1.016081 50.894741,-1.016068 50.894723,-1.016046 50.894709,-1.016018 50.894700,-1.015988 50.894697,-1.015957 50.894700,-1.015929 50.894708,-1.015907 50.894722,-1.015892 50.894739,-1.015887 50.894759)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL